chore: add MCP Registry submission files and per-client config snippets#12
Conversation
- Add server.json for official MCP Registry (io.github.commit-check/commit-check-mcp) - Add mcp-name HTML comment for PyPI ownership verification - Add MCP Registry and Glama badges to README header - Rewrite 'Use With An MCP Client' section with ready-to-use config snippets for: Claude Desktop, Claude Code CLI, Cursor, Windsurf, Cline, Continue.dev, Roo Code, and Zed - Recommend uvx as the primary zero-install runner - Add 'Published On' table with links to MCP Registry, Glama, PyPI - Add instructions for contributing to awesome-mcp-servers and Smithery
github-actions
Bot
added
chore
documentation
|
Warning Review limit reached
Next review available in: 24 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12 +/- ##
=======================================
Coverage 66.02% 66.02%
=======================================
Files 2 2
Lines 209 209
=======================================
Hits 138 138
Misses 71 71 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
2 participants
Summary
This PR addresses the lack of visibility for
commit-check-mcpin the MCP ecosystem. It adds everything needed for submission to the official MCP Registry and provides ready-to-use config snippets for mainstream MCP clients.Changes
1.
server.json— Official MCP Registry Submissionserver.jsonwith server metadata for the MCP Registryio.github.commit-check/commit-check-mcp(PyPI package type)runtimeHintforuvx2.
README.md— Ownership Verification<!-- mcp-name: io.github.commit-check/commit-check-mcp -->HTML comment (required by MCP Registry for PyPI ownership verification)3.
README.md— Per-Client Config SnippetsReplaced the generic single-config section with ready-to-copy-paste snippets for 8 mainstream clients:
claude_desktop_config.json~/.claude/settings.json.cursor/mcp.json~/.codeium/windsurf/mcp_config.json~/.continue/config.json~/.config/zed/settings.jsonAll snippets use
uvx commit-check-mcp(zero-install) as the recommended approach.4.
README.md— New Badges & "Published On" Section5.
README.md— Run Manually Updateuvx commit-check-mcpas the zero-install alternativePost-Merge Steps
After this PR is merged, the repo owner should publish to the MCP Registry:
Then submit PRs to add to community directories: